[monitoring] Expose prometheus via TCP services#1357
Merged
barroco merged 1 commit intointeruss:masterfrom Jan 20, 2026
Merged
Conversation
the-glu
force-pushed
the
monitoring_expose_prometheus_directly
branch
from
2df46bc to
934f757
Compare
barroco
approved these changes
Jan 20, 2026
the-glu
force-pushed
the
monitoring_expose_prometheus_directly
branch
from
934f757 to
6fb58a2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR change method of exposing prometheus externally with a simple L4 service, as prometheus handle directly authentification with certificates.
It does change the method on helm and tanka, and make helm and tanka at the same feature level.
This PR follow #1356 .